home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20010921-20020314
/
000302_fdc@columbia.edu_Mon Jan 21 15:46:09 EST 2002.msg
< prev
next >
Wrap
Text File
|
2002-03-13
|
3KB
|
68 lines
Article: 13137 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Using redirection when starting K95
Date: 21 Jan 2002 15:46:00 -0500
Organization: Columbia University
Lines: 51
Message-ID: <a2hum8$o2f$1@watsol.cc.columbia.edu>
References: <3d44a7c4.0201211200.7a8591b0@posting.google.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1011645961 26329 128.59.39.139 (21 Jan 2002 20:46:01 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 21 Jan 2002 20:46:01 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13137
In article <3d44a7c4.0201211200.7a8591b0@posting.google.com>,
Larry Mann <lvm@cowlitz.com> wrote:
:
: (I attempted to post a similar message earlier today it did appear to
: get listed so I am trying again)
:
It did appear and I did answer it, but so as not to appear unresponsive,
will answer it again, especially as this posting is not the same as your
first one.
: Some years ago I wrote several Unix shell scripts that called Kermit
: using redirection...
:
As noted in the C-Kermit book, this is not how to write scripts. It
prevents all sorts of things from working, like GOTO, certain kinds of
loops, etc.
: ... for both providing input from a Kermit script and
: any response output to a file. This was done with HP-UX and C-Kermit
: communicating with a remote Kermit server.
:
: I now need to move these scripts from HP-UX and C-Kermit to Windows
: 2000 Server and K95. I have installed a Unix shell on W2K and all is
: fine except the shell script lines that call Kermit, K95, do not seem
: to accept redirection, for example:
: k95 < in.ksc > out.txt
:
Because Kermit 95 is not a Unix program and does not read from stdin.
If it did, it wouldn't be able to see the full keyboard, which is a must
for any PC-based terminal program.
: where in.ksc contains and is communicating with a remote Kermit
: server:
: set line com1
: set baud 9600
: rem dir c:/temp
: This would capture a list of filenames from the remote server into
: out.txt for further processing in the shell script.
:
: I understand that I could provide the script name as the first item on
: the Kermit command line, such as: k95 in.ksc and that's fine...
: but how can I capture the standard output from this script to a file,
: out.txt?
:
Again:
rem dir c:/temp > filename
You could have done this in C-Kermit too.
- Frank